Transportation system including autonomous detachable engine modules and passenger module

ABSTRACT

A transportation system includes at least one passenger module and at least one autonomous engine module configured to operatively couple with the at least one passenger module to form an autonomous passenger vehicle.

TECHNICAL FIELD

The present invention relates to autonomous vehicles and, moreparticularly, to an engineless passenger module and a detachableautonomous engine module which is dockable with the passenger module toform an autonomous passenger vehicle.

BACKGROUND

Fully autonomous passenger vehicles are designed or contemplated whichare capable of driving themselves and any onboard passengers and/orcargo between locations without any input from a human driver. Howeverin an autonomous vehicle, there is no reason for a passenger or cargocompartment unless the vehicle is transporting passengers or cargo.Thus, unless the vehicle is transporting passengers or cargo, theautonomous vehicle may spend a large amount of time moving anessentially empty vehicle between locations. This is wasteful of fuel.

In addition, the transportation needs of a user may vary with a givensituation. If the user needs to tow a trailer, the user's conventionalpassenger vehicle may not have the capacity to effect the tow.Alternatively, the user's conventional passenger vehicle may be a pickuptruck or sport utility vehicle with an engine and transmissionengineered for transporting heavy loads. If the user wishes to take along trip carrying a light or moderate load along a route consistingpredominantly of expressway travel, a pickup truck or sport utilityvehicle may not be the best choice for such a trip. Thus, the engine andtransmission of a conventional passenger vehicle (even an automatedpassenger vehicle) is frequently not suited to the transportation needit is called upon to meet.

SUMMARY

In one aspect of the embodiments described herein, a transportationsystem is provided. The transportation system includes at least onepassenger module and at least one autonomous engine module configured tooperatively couple with the at least one passenger module to form anautonomous passenger vehicle.

In another aspect of the embodiments described herein, a computingsystem is provided. The system includes one or more processors forcontrolling operation of the computing system, and a memory for storingdata and program instructions usable by the one or more processors. Theone or more processors are configured to execute instructions stored inthe memory to determine, responsive to a request for use of anautonomous engine module, at least one autonomous engine module usecandidate from a plurality of autonomous engine modules.

In another aspect of the embodiments described herein, acomputer-implemented method is provided. The method includes a step ofdetermining, responsive to a request for use of an autonomous enginemodule, at least one autonomous engine module use candidate from aplurality of autonomous engine modules.

In another aspect of the embodiments described herein, a non-transitorycomputer readable medium is provided. The medium has stored thereininstructions executable by a computer system to cause the computersystem to perform functions, the functions comprising at leastdetermining, responsive to a request for use of an autonomous enginemodule, at least one autonomous engine module use candidate from aplurality of autonomous engine modules.

Embodiments of the transportation system described herein enable a userto customize and personalize a passenger module, which would bepropelled to a destination using an autonomous engine module. Anautonomous engine module may automatically dock with the passengermodule, propel the passenger module to a destination, park the passengermodule in a designated location, and detach itself from the passengermodule for a subsequent use elsewhere. The engine module may be selectedfrom a plurality of available engine module candidates based on theuser's particular need. The user may own the passenger module but doesnot own or maintain the engine module. The ability to forego ownershipof a vehicle having many or all of the high-maintenance vehicle systems(such as an engine and transmission) needed to propel the vehicle, andthe ability to specify an engine module optimized for a particular use,may combine to drastically reduce the costs of vehicle ownership.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of an exemplary computing systemconfigured for use in a transportation system according to one or moreillustrative embodiments of the disclosure.

FIG. 2 is a functional block diagram illustrating an autonomous enginemodule in accordance with an example embodiment.

FIG. 3 is a functional block diagram illustrating a passenger module inaccordance with an example embodiment.

FIGS. 4A-4C are schematic diagrams illustrating mating of embodiments ofelectrical/power connection modules and docking mechanisms duringdocking of an engine module with a passenger module, in accordance withcertain embodiments described herein.

FIG. 5 is a schematic block diagram of a transportation system inaccordance with one embodiment described herein.

FIG. 6 is a schematic block diagram of a transportation system inaccordance with another embodiment described herein.

FIG. 7 is a flow diagram illustrating a method of selecting an enginemodule based on a request for use, and of providing a selected enginemodule to a user for use at a desired time and place.

FIG. 8 is a schematic block diagram illustrating examples of enginemodule evaluation criteria usable for determining at least oneautonomous engine module use candidate from a plurality of autonomousengine modules, as described in block 510 of FIG. 7.

FIG. 9 is a flow diagram illustrating an example of a use candidatedetermination process which is prioritized and/or weighted, according topre-programmed instructions or by a user prior to determination of theengine module candidates.

FIG. 10 is a schematic view showing how a passenger module in accordancewith an embodiment described herein may be customized or personalizedaccording to the needs of an individual user.

FIGS. 11 and 11A show an alternative embodiment of a docking mechanismfor connecting and engine module with a passenger module.

FIG. 12 shows another alternative embodiment of a docking mechanism forconnecting and engine module with a passenger module.

DETAILED DESCRIPTION

Embodiments described herein relate to a transportation system andmethod for enabling a user to schedule the use of an engine module forpropelling a passenger module which is separable from the engine moduleand is securable to the engine module for transportation purposes. Theengine module includes a motive power system (i.e., engine,transmission, etc.), a braking system, a steering system, a throttlesystem, a computing system for control, and any other systems orelements needed for the engine module to implement an autonomousself-driving capability, for docking with and securing to a passengermodule, for providing power to the passenger module systems, fortransporting or propelling the passenger module from a start location toone or more destinations, and for any other engine module-relatedpurposes described herein. The engine module may not include anypassenger accommodations or driver-related features, such as a steeringwheel. The engine module may be configured only for self-driving andfully automated steering. The passenger module may incorporate anysystems or features usable or desirable by a passenger during a fullyautomated driving experience. The passenger module may not include anengine or means of propulsion, but rather relies on the engine modulefor propulsion.

FIG. 1 illustrates a block diagram of an exemplary computing system 13configured for use in a transportation system according to one or moreillustrative embodiments of the disclosure. The computing system 13 mayhave some or all of the elements shown in FIG. 1, and may also includeadditional components as needed or desired for particular applications.The computing system 13 may incorporate some or all of the elementsshown in FIG. 1 at a single location. Alternatively, the computingsystem 13 may represent or be embodied in a plurality of computing andrelated devices in operative communication with each other, which mayprocess information and/or perform the various functions describedherein in a distributed or decentralized fashion.

The computing system 13 may include one or more processors 13 e (whichcould include at least one microprocessor) for controlling overalloperation of the computing system 13 and associated components, andwhich execute instructions stored in a non-transitory computer readablemedium, such as the memory 13 a. “Processor” means any component orgroup of components that are configured to execute any of the processesand/or process steps described herein or any form of instructions tocarry out such processes/process steps or cause such processes/processsteps to be performed. The processor(s) 13 e can include at least onehardware circuit (e.g., an integrated circuit) configured to carry outinstructions contained in program code. In arrangements in which thereis a plurality of processors 13 e, such processors can workindependently from each other or one or more processors can work incombination with each other.

In some embodiments, the computing system 13 may include RAM 13 g, ROM13 f, and/or any other suitable form of computer-readable memory. Thememory 13 a may comprise one or more computer-readable memories. Acomputer-readable storage or memory 13 a includes any medium thatparticipates in providing data (e.g., instructions), which may be readby a computer. Such a medium may take many forms, including, but notlimited to, non-volatile media, volatile media, etc. The memory ormemories 13 a can be a component of the computing system 13, or thememory or memories can be operatively connected to the computing system13 for use thereby. The term “operatively connected,” as used throughoutthis description, can include direct or indirect connections, includingconnections without direct physical contact.

The memory 13 a may contain data 13 d and/or instructions 13 c (e.g.,program logic) executable by the processor(s) 13 e to execute one ormore of the various functions described herein. The memory 13 a maycontain additional instructions as well, including instructions to(directly or through communications interfaces 13 k) transmitinformation to, receive information from, interact with or control oneor more of the various autonomous engine modules, users, and/orpassenger modules as described herein. In addition to the instructions13 c, the memory 13 a may store data such as roadway maps and pathinformation, among other information. Such information may be used bythe computing system (either alone or in conjunction with an associatednavigation capability 13 h) in calculating and evaluating various routesthat may taken by the engine modules prior to or during transportationof a passenger module for a given application. The navigation capability13 h may be incorporated into the computing system 13, or the navigationcapability 13 h may be embodied in a separate navigation unit (notshown) in operative communication with the computing system. Also, thememory 13 a may incorporate an embodiment of an engine module usecandidate determination capability 13 b, as described in greater detailbelow.

In one or more arrangements, the computing system 13 described hereincan incorporate artificial or computational intelligence elements, e.g.,neural network, reinforcement learning or other machine learningalgorithms. Further, in one or more arrangements, the hardware and/orsoftware elements configured for performing particular functions oroperations described herein may be distributed among a plurality ofelements and/or locations.

Computing system 13 may operate in a networked environment supportingconnections to one or more remote computers, such as other computingdevices, terminals and/or mobile devices (e.g., mobile phones,short-range vehicle communication systems, vehicle telematics devicesand vehicle-to-vehicle communications systems) (not shown). Any othercomputing systems or devices in operative communication with computingsystem 13 may include devices installed in vehicles, mobile devices thatmay travel within vehicles, or devices outside of vehicles. Thus, anyterminals or devices in operative communication with the computingsystem 13 may each include personal computers (e.g., laptop, desktop, ortablet computers), servers (e.g., web servers, database servers),vehicle-based devices (e.g., on-board vehicle computers, short-rangevehicle communication systems, telematics devices), or mobilecommunication devices (e.g., mobile phones, portable computing devices,suitably-configured wearable devices (such as a watchband and the like)(not shown), and may include or be configured to interface with some orall of the elements described above with respect to the computing system13. In addition, any of these device embodiments may include a hapticinterface or may be configured to provide haptic feedback to a user toinform the user of any information or condition which should becommunicated to a user of any transportation system embodiment describedherein.

Communications interfaces 13 k may be configured to enable interactionbetween the computing system 13 and any users of an embodiment of thetransportation system, any passenger modules and autonomous enginemodules which are part of a network, other computing systems, andvarious external messaging and communications systems (such as satelliteand navigation systems, cellular or wireless communication systems, andany other systems or elements which may facilitate performance of thefunctions described herein). The communications interfaces 13 k may beincorporated into the computing system 13 or may be located spaced apartfrom the computing system and communicatively coupled to the computingsystem. The communications interfaces 13 k may be configured tocommunicate with various message servers or message storage andretrieval entities (not shown) tasked for storing messages transmittedto or from one or more engine modules, passenger modules an owner/userand/or other entities.

The communications interfaces 13 k may include a user interface forproviding information to or receiving input from a user of thetransportation system. For example, the communications interfaces 13 kmay include a voice/audio interface (not shown) (for example, amicrophone and speaker for providing audio input and output), keypad,touch screen, and/or stylus through which a user of the computing system13 may provide input, and may also include and a video display device(not shown) for providing textual, audiovisual and/or graphical outputfrom the computing system. The computing system 13 may be configured tointerpret or process any received audio input as a response to a queryor an instruction for the computing system. The user interface maycontrol or enable control of content and the layout of interactiveimages that may be displayed on the display. A display in the form of atouch screen may provide information to a user of the transportationsystem, and may also be operable to accept input from the user via thetouch screen. The display can also be any other suitable type ofdisplay.

The communications interfaces 13 k may also include interfaces enablingcommunication in a wide area network (WAN), one or more wirelesstelecommunications networks, and/or other communications networks. Whenused in a WAN networking environment, the computing system 13 mayinclude (or be operatively connected to) a modem or other means forestablishing communications over the WAN. When used in a wirelesstelecommunications network, the computing system 13 may include (or beoperatively connected to) one or more transceivers, digital signalprocessors, and additional circuitry and software for communicating withwireless computing devices (not shown) via one or more network devices(e.g., base transceiver stations) in the wireless network. Theseconfigurations provide various ways of receiving information fromexternal various sources. The communication networks can also includewired communication links. The communication network(s) can include anycombination of the above networks and/or other types of networks.

FIG. 2 is a functional block diagram illustrating an autonomous enginemodule 11 in accordance with an example embodiment. The engine modulemay be configured for completely autonomous driving operations (i.e.,for self-driving, without the presence of a driver or any human input)from a start location to a given destination along a route determined bya navigation unit or system, for example. The engine module may beconfigured to operate the throttle, braking and other systems duringperformance of self-driving operations.

Embodiments of the engine module described herein may also includesystems and components needed for determining one or more routes forself-driving; for communicating with various users, computing systems,passenger modules, other engine modules, and other entities; for dockingwith a passenger module, and for propelling the passenger module asdescribed herein. The engine module embodiments may not be configuredfor transporting passengers by themselves, without an attached passengermodule. Thus, features and accommodations designed for passengers anddrivers and appearing in conventional motor vehicles may not be includedin the engine module embodiments described herein.

The engine module 11 may include various systems, subsystems andcomponents in operative communication with each other, such as a sensorsystem or array 28, a computing system 14, one or more communicationsinterfaces 16, a steering system 18, a throttle system 20, a brakingsystem 22, a power supply 30, a motive power system 26, and othersystems and components needed for operating the engine module asdescribed herein. The engine module 11 may include more or fewersubsystems and each subsystem could include multiple elements. Further,each of the subsystems and elements of engine module 11 could beinterconnected. Thus, one or more of the described functions of theengine module 11 may be divided up into additional functional orphysical components or combined into fewer functional or physicalcomponents.

The sensor system 28 may include a number of sensors configured to senseinformation about an external environment of the engine module 11.Sensors of engine module sensor system 28 may include any sensorsrequired to support any self-driving capabilities and/or associatedautonomous capabilities incorporated into the engine module 11. Variousexamples of different types of sensors are described herein. However, itwill be understood that the embodiments are not limited to theparticular sensors described. In arrangements in which the sensor system28 includes a plurality of sensors, the sensors can work independentlyfrom each other, or two or more of the sensors can work in combinationwith each other. Sensors of the sensor system 28 may be operativelyconnected to the computing system 14 and/or any other element of theengine module 11.

For example, the sensor system 28 may include a navigation unit 28 nsuch as a Global Positioning System (GPS), an inertial measurement unit(IMU), a RADAR unit, a laser rangefinder/LIDAR unit, and one or morecameras comprising devices configured to capture a plurality of imagesof an external environment of the engine module 11. The camera(s) may bestill cameras or video cameras. The IMU may incorporate any combinationof sensors (e.g., accelerometers and gyroscopes) configured to senseposition and orientation changes of the engine module 11 based oninertial acceleration. For example, the IMU may sense such parameters asthe roll rate, yaw rate, pitch rate, longitudinal acceleration, lateralacceleration, and vertical acceleration of an engine module or an enginemodule and passenger module attached thereto.

The navigation unit may be any sensor or sensors configured to estimatea geographic location of the engine module 11. The navigation unit mayalso be configured to determine or plan a driving route from a givenstart point (for example, a current location of the engine module oranother designated start location) to a selected destination, usingstored and/or available maps, in a manner known in the art. To theseends, the navigation unit may include a one or more transceivers,including a transceiver operable to provide information regarding theposition and/or movement of the engine module 11 with respect to Earth.

In addition, if desired, docking sensors 28 a may be provided to aid indocking the engine module 11 with a passenger module. The dockingsensors 28 a may include any suitable type of sensor, including cameras(with an associated image processing capability included in computingsystem 14), proximity sensors, and/or other sensors designed to aid inpositioning the engine module prior to and during docking, and forconfirming that mechanical and electrical docking have taken place.

In a known manner, the various engine module sensors 28 may provide dataused by the engine module computing system 14 in formulating andexecuting suitable control commands for the various engine modulesystems. For example, data from inertial sensors, wheel speed sensors,road condition sensors, and steering angle sensors may be processed informulating and executing a command in steering system 18 to turn theengine module.

Information from particular engine module sensors may be processed andused to control more than one engine module system or component. Forexample, various road condition sensors may be provided to supplyinformation to the engine module computing system to enable thecomputing system to process the road condition information in accordancewith stored processor-executable instructions, and to formulateappropriate control commands to both the steering system and brakingsystem. The computing system 14 may continuously receive and process anongoing or continuous flow of information from sensor system 28 and fromother information sources. This information is processed and/orevaluated in accordance with instructions stored in a memory, in amanner and for the purposes described herein. The use of “continuously”when referring to the reception, gathering, monitoring, processing,and/or determination of any information or parameters described hereinmeans that the computing system 14 is configured to receive and/orprocess any information relating to these parameters as soon as theinformation exists or is detected, or as soon as possible in accordancewith sensor acquisition and processor processing cycles.

The engine module 11 may include a suitable signal processing capability38 for situations where a sensor output signal or other signal requirespre-processing prior to use by the computing system or another enginemodule system or element, or where a control signal sent from thecomputing system will require processing prior to use by actuatablesub-systems or sub-system components (for example, components of thesteering system or throttle system). The signal processing capabilitymay be an analog-to-digital (A/D) converter or digital-to-analog (D/A)converter, for example.

A sensor fusion algorithm 138 may be an algorithm (or a computer programproduct storing an algorithm) configured to accept data from the sensorsystem 28 as an input. The data may include, for example, datarepresenting information sensed at the sensors of the sensor system 28.The sensor fusion algorithm may process data received from the sensorsystem to generate an integrated or composite signal (formed, forexample, from outputs of multiple individual sensors). The sensor fusionalgorithm 138 may include, for instance, a Kalman filter, a Bayesiannetwork, or another algorithm. The sensor fusion algorithm 138 mayfurther provide various assessments based on data from the sensor system28. In an example embodiment, the assessments may include evaluations ofindividual objects or features in the environment of the engine module11, evaluation of a particular situation, and evaluation of possibleimpacts based on the particular situation. Other assessments are alsopossible. The sensor fusion algorithm 138 may be stored on a memory(such as memory 54) incorporated into or in operative communication withcomputing system 14, and may be executed by the computing system in amanner known in the art.

FIG. 2 also illustrates a block diagram of an engine module computingsystem 14 according to one or more illustrative embodiments of thedisclosure. The computing system embodiment shown in FIG. 2 may beconfigured similarly to the computing system embodiment shown in FIG. 1.However, the engine module computing system may be configured in anymanner suitable for the purposes described herein.

The computing system 14 may have some or all of the elements shown inFIG. 2. In addition, the computing system 14 may also include additionalcomponents as needed or desired for particular applications. Thecomputing system 14 may also represent or be embodied in a plurality ofcontrollers or computing devices that may process information and/orserve to control individual components or subsystems of the enginemodule 11 in a distributed fashion.

The engine module computing system 14 may be operatively connected tothe other engine module systems and elements and otherwise configured soas to affect control and operation of the engine module 11 and itscomponents as described herein. The computing system 14 may control thefunctioning of the engine module systems and/or components autonomously(without human input), based on inputs and/or information received fromvarious subsystems (e.g., motive power system 26, sensor system 28,steering system 18, etc.), from any of the communications interfaces 16,and/or from any other suitable source of information. The computingsystem may also be configured to autonomously control and/or executecertain additional functions.

The computing system 14 may include one or more processors 58 (whichcould include at least one microprocessor) for controlling overalloperation of the computing system 14 and associated components, andwhich executes instructions stored in a non-transitory computer readablemedium, such as the memory 54. The processor(s) 58 can include at leastone hardware circuit (e.g., an integrated circuit) configured to carryout instructions contained in program code. In arrangements in whichthere is a plurality of processors 58, such processors can workindependently from each other or one or more processors can work incombination with each other. In one or more arrangements, theprocessor(s) 58 can be main processor(s) of the engine module 11. Forinstance, the processor(s) 58 can be part of an electronic control unit(ECU).

The computing system 14 may include RAM 50, ROM 52, and/or any othersuitable form of computer-readable memory. The memory 54 may compriseone or more computer-readable memories. A computer-readable storage ormemory 54 includes any medium that participates in providing data (e.g.,instructions), which may be read by a computer. Such a medium may takemany forms, including, but not limited to, non-volatile media, volatilemedia, etc. The memory or memories 54 can be a component of thecomputing system 14, or the memory or memories can be operativelyconnected to the computing system 14 for use thereby.

The memory 54 may contain data 60 and/or instructions 56 (e.g., programlogic) executable by the processor(s) 58 to execute various functions ofthe engine module 11. The memory 54 may contain additional instructionsas well, including instructions to (directly or through communicationsinterfaces 16) transmit information to, receive information from,interact with, or control one or more of the engine module systemsand/or components described herein (for example, motive power system 26,sensor system 28, computing system 14, and the communication interfaces16). In addition to the instructions 56, the memory 54 may store datasuch as roadway maps, path information, among other information. Suchinformation may be used by the computer system 14 (either alone or inconjunction with an associated navigation unit 28 n) in calculating andevaluating various routes that may taken by the engine module prior toor during transportation of a passenger module for a given application.

The computing system 14 may be configured to coordinate control of thevarious actuatable engine module systems and components so as toimplement one or more autonomous capabilities (generally designated 62),including a self-driving capability 83. These autonomous capabilities 62may be stored in memory 54 and/or in other memories and implemented inthe form of computer-readable program code that, when executed by aprocessor, implement one or more of the various processes, instructionsor functions described herein.

For example, the self-driving capability 83 may enable autonomousoperation of the engine module 11 so as to drive the module from itscurrent location to any specified end location. U.S. application Ser.No. 14/789,004, the disclosure of which is incorporated herein byreference in its entirety, describes methods and systems usable forcontrolling an autonomously operable vehicle while traveling from astart location to a designated end location. Other methods and systemsmay be used instead of or in addition to the methods and systemsdescribed in the '004 application. The engine module computing system 14may be configured to (responsive to inputs from the navigation unit 28 nand from other sensors, such as cameras) operate the engine module 11 inaccordance with traffic lights and traffic signs along the planned routeand to perform any other operations and functions necessary forself-driving the engine module to and from designated locations. Thenavigation unit 28 n and other information sources (for example,real-time traffic information sources) may be accessed to provide otherinformation usable by the computing system 14.

The memory 54 may also include an embodiment 71 of an engine module usecandidate determination capability, as described in greater detailbelow. The memory 54 may also include an automated docking capability 73which may be implemented for docking the engine module to the passengermodule.

In one or more arrangements, the computing system 14 can incorporateartificial or computational intelligence elements, e.g., neural network,reinforcement learning or other machine learning algorithms. Further, inone or more arrangements, the hardware and/or software elementsconfigured for performing particular functions or operations describedherein may be distributed among a plurality of elements and/orlocations.

Computing system 14 may operate in a networked environment supportingconnections to one or more remote computers, such as other computingdevices, terminals and/or mobile devices (e.g., mobile phones,short-range vehicle communication systems, telematics devices andvehicle-to-vehicle communications systems) (not shown). Any computingsystems or devices in operative communication with computing system 14may include devices installed in vehicles, mobile devices that maytravel within vehicles, or devices outside of vehicles that areconfigured to perform and/or support performance of the operations andfunctions described herein. Thus, any terminals or devices in operativecommunication with the computing system 14 may each include personalcomputers (e.g., laptop, desktop, or tablet computers), servers (e.g.,web servers, database servers), vehicle-based devices (e.g., on-boardvehicle computers, short-range vehicle communication systems, telematicsdevices), or mobile communication devices (e.g., mobile phones, portablecomputing devices, suitably-configured wearable devices (such as awatchband and the like) (not shown), and may include some or all of theelements described above with respect to the computing system 14. Inaddition, any of these device embodiments may include a haptic interfaceor may be configured to provide haptic feedback to a vehicle occupant toinform the occupant of any information or condition which should becommunicated to a user of a transportation system as described herein.

Communications interfaces 16 may be configured to allow interactionbetween the engine module 11 and external sensors, other vehicles, othercomputer systems, various external messaging and communications systems(such as a satellite system, a cellular phone/wireless communicationsystem, etc.) and/or a user. The communications interfaces 16 may beconfigured to communicate with various message servers or messagestorage and retrieval entities, for storing messages transmitted to orfrom the engine module, a computing system outside the engine module, auser, and/or other entities. For example, messages directed to theengine module and not received by the engine module when the enginemodule is turned off, may be stored off-module for retrieval by theengine module computing system when the engine module is turned on. Thisaids in conserving engine module battery power by enabling the enginemodule communications systems to be deactivated when the engine is off.Alternatively, if desired, the communications systems features andelements needed for messaging may be powered by the engine module powersupply 30 or by other means when the engine is off. This capability ofthe engine module may be enabled through a user interface with theengine module computing system, for example.

The communications interfaces 16 may include one or more interfaces forproviding information to computing system 14 or receiving input fromanother engine module, a user of the engine module 11 or of thetransportation system of the engine module, or any other entity. Thecommunications interfaces 16 may also include interfaces enablingcommunication in a wide area network (WAN), a wirelesstelecommunications network, and/or other communications networks. Thecommunication network(s) can also include wired communication links. Thecommunication network(s) can include any combination of the abovenetworks and/or other types of networks. When used in a WAN networkingenvironment, the computing system 14 may include (or be operativelyconnected to) a modem or other means for establishing communicationsover the WAN, such as network (e.g., the Internet). When used in awireless telecommunications network, the computing system 14 may include(or be operatively connected to) one or more transceivers, digitalsignal processors, and additional circuitry and software forcommunicating with wireless computing devices (not shown) via one ormore network devices (e.g., base transceiver stations) in the wirelessnetwork. These configurations provide various ways of receiving aconstant flow of information from various external sources.

In one or more arrangements, the communication network(s) can includeVehicle-to-Everything (V2X) technologies (includingVehicle-to-Infrastructure (V2I) and Vehicle-to-Vehicle (V2V)technologies), which can allow for communications between any nearbyvehicle(s), and the engine module 11 and any nearby roadsidecommunications nodes and/or infrastructure.

The engine module 11 may include various actuatable sub-systems andelements in operative communication with computing system 14 and otherengine module systems and/or components, and which are operableresponsive to control commands received from the computing system.Various actuatable sub-systems and elements may be controlledautomatically by computing system 14. FIG. 2 shows just a few examplesof actuatable sub-systems 18, 20, 22, 26 which may be incorporated intoan engine module. A particular engine module may incorporate one or moreof these systems or other systems (not shown) in addition to one or moreof the systems shown.

The steering system 18 may include such elements as the engine modulewheels, servo-mechanisms, gears, steering knuckles, and/or any otherelements or combination of elements that may be operable to enableautonomous adjustment of the heading of engine module 11. As the enginemodule is operated fully autonomously, a steering wheel and componentsneeded to guide the vehicle using a steering wheel may be omitted.

The motive power system 26 may include components operable to providepowered motion for the engine module 11. In an example embodiment, themotive power system 26 may include an engine (not shown), an energysource (such as gasoline, diesel fuel, hydrogen fuel cell, or a one ormore electric batteries in the case of a hybrid engine module), and atransmission (not shown). The engine may be any of (or a combination of)an internal combustion engine, an electric motor, steam engine, Stirlingengine, a pure electric engine (i.e., an engine powered by batteries,for example), or other types of engines or motors. In some exampleembodiments, the motive power system 26 may include multiple types ofengines or motors. For instance, a gas-electric hybrid car could includea gasoline engine and an electric motor. Other examples are possible.

The engine, transmission, and other motive power-related components inany given engine module may be optimized at least to some degree for aparticular type of use. At the same time, the number of different enginemodule types may be limited to as few as possible, to help minimizeengine module production and operating expenses.

For example, in certain embodiments of the transportation system, eachengine module may be optimized to either generate a relatively hightorque, to provide a relatively high fuel-efficiency, or to generate arelatively high horsepower. In a particular embodiment, one or more ofthe engine modules may be optimized to generate a relatively high torqueand a relatively high horsepower. This element of specialization may aidthe process of determining suitable engine module use candidates, whilealso helping to identify the most effective and/or cost-efficient enginemodule(s) for a particular use.

In one example, an engine module optimized or configured for generatinga relatively high torque may be the best selection for an applicationinvolving the transportation of heavy loads or in a towing application.An engine module optimized or configured for generating a relativelyhigh horsepower may be the best selection for relatively low-load,higher-speed applications. One example of such a high horsepowerapplication may be travel in a dedicated high-speed traffic lane (forexample, at speeds of up to 200 miles per hour). An engine moduleoptimized or configured for providing a relatively high fuel-efficiencymay be the best selection for longer trips at relatively constantspeeds, or for city driving.

In certain embodiments described herein, engine modules optimized forgenerating a relatively high torque may form a class of engine moduleswherein each module in the class may generate a torque within apredetermined range or above a predetermined threshold. Similarly,engine modules optimized for generating a relatively high horsepower mayform a class of engine modules wherein each module in the class maygenerate a horsepower within a predetermined range or above apredetermined threshold. Also, engine modules optimized for providing arelatively high fuel-efficiency may form a class of engine moduleswherein each module in the class provides a fuel-efficiency within apredetermined range or above a predetermined threshold. The computingsystem embodiments described herein may be configured for evaluatingparameters of the requested use and identifying the best engine moduleuse candidates for a given application, using these thresholds andmethods described herein or other suitable methods.

The braking system 22 could include any combination of elements and/ormechanisms configured to autonomously decelerate the engine module 11.The-braking system may include couplings (for example, hydraulic,electrical, and/or pneumatic couplings) (not shown) configured foroperatively connecting the engine module braking system to brakesincorporated into the passenger module (for example, on the module rearwheels). This may enable the engine module braking system to power apassenger module braking system to aid in slowing and stopping theautonomous passenger vehicle created by joining the passenger module tothe autonomous engine module.

The throttle system 20 may include elements and/or mechanisms configuredto autonomously control, for instance, the operating speed of the engineand, in turn, control the speed of the engine module 11. The powersupply 30 may provide power to various components of the engine module11 and could represent, for example, a rechargeable lithium-ion orlead-acid battery. In some embodiments, one or more banks of suchbatteries could be configured to provide electrical power. Other powersupply materials and configurations are possible.

The engine module 11 may be configured so that the computing system 14,sensor system 28, actuatable sub-systems 18, 20, 22, 26 and othersystems and elements thereof can communicate with each other using acontroller area network (CAN) bus 33 or the like. Via the CAN bus and/orother wired or wireless mechanisms, the computing system 14 may transmitmessages to (and/or receive messages from) the various engine modulesystems and components. Alternatively, any of the elements and/orsystems described herein may be directly connected to each other withoutthe use of a bus. Also, connections between the elements and/or systemsdescribed herein may be through another physical medium (such as wiredconnections) or the connections may be wireless connections.

FIG. 3 is a functional block diagram illustrating a passenger module 99in accordance with an example embodiment. The passenger module 99 isconfigured to be dockable with any of a plurality of engine modules,according to the requirements of a particular driving situation asdescribed herein. The passenger module may be customized, personalized,and otherwise configured by a user or owner according to personalpreferences. In addition, user-accessible cargo space (for example,trunk or other space) may be increased. Also, because the passengermodule 99 is propelled in a driverless mode, the module may be loadedwith only cargo and transported to a desired destination. In at leastsome embodiments described herein, the passenger module may have noengine, motor, or other means of self-propulsion, since theseembodiments of the passenger module are designed to use a connectedautonomous engine module as the means of propulsion.

The passenger module 99 may include various systems, subsystems andcomponents in operative communication with each other, such as a sensorsystem or array 128, a computing system 114, one or more communicationsinterfaces 116, a braking system 122, a power supply 930, and othersystems and components needed for operating the passenger module 99 asdescribed herein. In the example shown in FIG. 3, the passenger module99 also includes a heating, ventilation and air conditioning (HVAC)system 142, an entertainment system 132, an exterior lighting system134, an interior lighting system 136, and may also include other systems(not shown). The entertainment system 132 may include any audio and/orvisual devices (for example, DVD players, radios, associated speakersystems,) usable for entertainment by the passenger module occupants.The passenger module internal user power system 140 includes elementssuch as the cigarette lighter, A/C power outlets, USB ports, and similarfeatures.

Each of the subsystems and elements of passenger module 99 may beinterconnected. Thus, one or more of the described functions of thepassenger module 99 may be divided up into additional functional orphysical components or combined into fewer functional or physicalcomponents. In some further examples, additional functional and physicalcomponents may be added to the examples illustrated by FIG. 3.

Passenger module sensors system 128 may include any sensors required tosupport any autonomous driving operations and/or other driving-relatedactivities of an engine module attached to the passenger module 99.Various examples of different types of sensors are described herein.However, it will be understood that the embodiments are not limited tothe particular sensors described. In arrangements in which the sensorsystem 128 includes a plurality of sensors, the sensors can workindependently from each other. Alternatively, two or more of the sensorscan work in combination with each other. In a known manner, thepassenger module sensor system 128 may provide data usable by thepassenger module computing system 114 in formulating and executingsuitable control commands for the various passenger module systems.

The sensor system 128 may include a number of sensors configured tosense information about the internal and external environments of thepassenger module 99. The sensor system 128 may include docking sensors128 a and other sensors 128 b, such as a navigation unit (for example, aGlobal Positioning System (GPS), a RADAR unit, a laser rangefinder/LIDARunit, an IMU, and one or more cameras comprising devices configured tocapture a plurality of images of the interior of the passenger module 99and/or an external environment of the module. The camera(s) may be stillcameras or video cameras. The navigation unit may be any sensorconfigured to estimate a geographic location of the passenger module 99.To this end, the navigation unit may include a one or more transceivers,including a transceiver operable to provide information regarding thegeographical location of the passenger module 99. The passenger modulemay also incorporate other sensors, if desired.

The passenger module sensor system 128 and computing system 114 may beconfigured for communicative coupling with the sensor system andcomputing system of an engine module to which the passenger module isattached (for example, sensor system 28 and computing system 14 of FIG.2, previously described). This enables the passenger module sensors toserve as extensions of the engine module sensors (for example, indetecting vehicles of other objects behind the passenger module duringtravel). Certain other elements on the passenger module (for example,exterior lighting and signals and certain sensors) may also beoperatively coupled to an engine module computing system 14 duringtravel, so that these elements may be controlled by the computing system14. Sensors of sensor system 128 may also monitor the temperature,humidity, ambient light levels and other characteristics of the moduleinterior, for use in controlling module environmental conditions.

The passenger module 99 may include a suitable signal processing means139 for situations where a sensor output signal or other signal requirespre-processing prior to use by the computing system 114 or anothervehicle system or element, or where a control signal sent from thecomputing system will require processing prior to use by actuatablesub-systems or sub-system components (for example, components of theHVAC system). The signal processing means may be an analog-to-digital(A/D) converter or digital-to-analog (D/A) converter, for example.

The computing system 114 may be operatively connected to the otherpassenger module systems and elements and otherwise configured so as toaffect control and operation of the passenger module 99 and itscomponents as described herein. The computing system 114 may beconfigured to control at least some systems and/or componentsautonomously (without user input) and/or semi-autonomously (with somedegree of user input). The computing system 114 may also be configuredto control and/or execute certain functions autonomously and/orsemi-autonomously. The computing system 114 may additionally oralternatively include components other than those shown and described.

FIG. 3 also illustrates a block diagram of an exemplary passenger modulecomputing system 114 according to one or more illustrative embodimentsof the disclosure. The computing system 114 may have some or all of theelements shown in FIG. 3. In addition, the computing system 114 may alsoinclude additional components as needed or desired for particularapplications. The computing system 114 may include one or moreprocessors 158 (which could include at least one microprocessor) forcontrolling overall operation of the computing system 114 and associatedcomponents, and which executes instructions stored in a non-transitorycomputer readable medium, such as the memory 154. In arrangements inwhich there is a plurality of processors 158, such processors can workindependently from each other or one or more processors can work incombination with each other.

In some embodiments, the computing system 114 may include RAM 150, ROM152, and/or any other suitable form of computer-readable memory. Thememory 154 may comprise one or more computer-readable memories. Acomputer-readable storage or memory 154 includes any medium thatparticipates in providing data (e.g., instructions), which may be readby a computer. Such a medium may take many forms, including, but notlimited to, non-volatile media, volatile media, etc. Non-volatile mediainclude, for example, optical or magnetic disks and other persistentmemory. The memory or memories 154 can be a component of the computingsystem 114, or the memory or memories can be operatively connected tothe computing system 114 for use thereby.

The memory 154 may contain data 160 and/or instructions 156 (e.g.,program logic) executable by the processor(s) 158 to execute variousfunctions of the passenger module 99, including those described above inconnection with FIG. 3. The memory 154 may contain additionalinstructions as well, including instructions to transmit data to,receive data from, interact with, or control one or more of thepassenger module systems and/or components described herein (forexample, entertainment system 132 and HVAC system 142, sensor system128, computing system 114, and the communication interfaces 116). Inaddition to the instructions 156, the memory 154 may store data such asroadway maps, path information, among other information. Suchinformation may be used by the computer system 114 at during travel.

In one or more arrangements, the computing system 114 described hereincan incorporate artificial or computational intelligence elements, e.g.,neural network, fuzzy logic or other machine learning algorithms.Further, in one or more arrangements, the hardware and/or softwareelements configured for performing particular functions or operationsdescribed herein may be distributed among a plurality of elements and/orlocations. In addition to computing system 114, the passenger module 99may incorporate additional computing systems and/or devices (not shown)to augment or support the control functions performed by computingsystem 114, or for other purposes.

Communications interfaces 116 may be configured to allow interactionbetween the passenger module 99 and engine modules, other passengermodules, other computer systems, various external messaging andcommunications systems (such as a satellite system or cellularphone/wireless communication system) and/or a user. The communicationsinterfaces 116 may include a user interface for providing information toor receiving input from a user of the passenger module 99. For example,the communications interfaces 116 may include a voice/audio interface119 (for example, a microphone and speaker for providing audio input andoutput), keypad, touch screen, and/or stylus through which a user of thecomputing system 114 may provide input, and may also include and a videodisplay device 117 for providing textual, audiovisual and/or graphicaloutput from the computing system 114. The computing system 114 may beconfigured to interpret or process any received audio input as aresponse to a query or an instruction for the computing system. The userinterface may control or enable control of content and the layout ofinteractive images that may be displayed on the display. A display inthe form of a touch screen may provide information to a user of thepassenger module 99. The user interface could also be operable to acceptinput from the user via the touch screen. The display can be any othersuitable type of display. For instance, the display can be a liquidcrystal display (LCD), a light emitting diode (LED) display or someother suitable display. In one or more arrangements, the display can bea heads-up display, a display for a navigation system, and/or a displayincluded in an instrument cluster. The display(s) can be provided in anysuitable location within the passenger module 99.

Computing system 114 may operate in a networked environment supportingconnections to one or more remote computers, such as other computingdevices, terminals and/or mobile devices (e.g., mobile phones,short-range vehicle communication systems, vehicle telematics devicesand vehicle-to-vehicle communications systems) (not shown). Any othercomputing systems or devices in the passenger module and any relatedterminals or devices in operative communication with computing system114 may include devices installed in vehicles, mobile devices that maytravel within vehicles, or devices outside of vehicles that areconfigured to communicate with passenger module 99. Thus, any terminalsor devices in communication with the computing system 114 may eachinclude personal computers (e.g., laptop, desktop, or tablet computers),servers (e.g., web servers, database servers), vehicle-based devices(e.g., on-board vehicle computers, short-range vehicle communicationsystems, telematics devices), or mobile communication devices (e.g.,mobile phones, portable computing devices, suitably-configured wearabledevices (such as a watchband and the like) (not shown), and may includesome or all of the elements described above with respect to thecomputing system 114. In addition, any of these device embodiments mayinclude a haptic interface or may be configured to provide hapticfeedback to a passenger module occupant to inform the occupant of anyinformation or condition which should be communicated to the occupant.

The communications interfaces 116 may also include interfaces enablingcommunication in a wide area network (WAN), a wirelesstelecommunications network, and/or any other communications networks.The communication network(s) can include any combination of the abovenetworks and/or other types of networks. In one or more arrangements,the communication network(s) can include Vehicle-to-Everything (V2X)technologies (including Vehicle-to-Infrastructure (V2I) andVehicle-to-Vehicle (V2V) technologies), which can allow forcommunications between any nearby vehicle(s), and the passenger module99 and any nearby roadside communications nodes and/or infrastructure.When used in a WAN networking environment, the computing system 114 mayinclude (or be operatively connected to) a modem or other means forestablishing communications over the WAN, such as network (e.g., theInternet). When used in a wireless telecommunications network, thecomputing system 114 may include (or be operatively connected to) one ormore transceivers, digital signal processors, and additional circuitryand software for communicating with wireless computing devices (notshown) via one or more network devices (e.g., base transceiver stations)in the wireless network. These configurations provide various ways ofreceiving a constant flow of information from external various sources.

The passenger module 99 may include various actuatable sub-systems andelements in operative communication with computing system 114 and otherpassenger module systems and/or components, and which are operable (atleast to some degree) responsive to control commands received from thecomputing system. Various actuatable sub-systems and elements may becontrolled manually or automatically (by computing system 114).

The braking system 122 could include any combination of elements and/ormechanisms configured to decelerate the passenger module 99. The brakingsystem 122 could use friction to slow the wheels. In other embodiments,the braking system 122 may convert the kinetic energy of the wheels toelectric current. The braking system 122 may take other forms as well. Aparticular vehicle may incorporate additional actuatable systems. Thebraking system may include couplings (for example, suitable electricaland/or hydraulic couplings) enabling connection to the engine modulebraking system and computer system 14, to enable control of thepassenger module brakes by the engine module computing system 14.

The passenger module power supply 930 may provide power to variouscomponents of the passenger module 99 and could represent, for example,a rechargeable lithium-ion or lead-acid battery. In some embodiments,one or more banks of such batteries could be configured to provideelectrical power. Other power supply materials and configurations arepossible. In certain embodiments, the passenger module 99 may includeany transformers or power conversion circuitry needed to enable thepower supply 930 and/or the passenger module systems to be plugged intoa standard A/C outlet, in a garage, for example. This enables thepassenger module systems to be utilized even when an engine module isnot connected to the passenger module 99. In some embodiments, thepassenger module 99 may incorporate an induction coil and associatedcircuitry for an induction charging system, or another wireless chargingor powering system.

The passenger module 99 may be configured so that the computing system114, sensor system 128, actuatable sub-systems and other systems andelements thereof can communicate with each other using a controller areanetwork (CAN) bus 133 or the like. Via the CAN bus and/or other wired orwireless mechanisms, the computing system 114 may transmit messages to(and/or receive messages from) the various passenger module systems andcomponents. Alternatively, any of the elements and/or systems describedherein may be directly connected to each other without the use of a bus.Also, connections between the elements and/or systems described hereinmay be through a physical medium (such as wired connections) or theconnections may be wireless connections.

Although FIG. 3 shows various components of passenger module 99,computing system 114, memory 154, and communications interfaces 116, asbeing integrated into the passenger module, one or more of thesecomponents could be mounted or associated separately from the passengermodule 99. For example, processors 158 or memory 154 could, in part orin full, exist separate from the passenger module 99. Thus, thepassenger module 99 could be provided in the form of device elementsthat may be located separately or together. The device elements thatmake up passenger module 99 could be communicatively coupled together ina wired or wireless fashion.

FIG. 10 illustrates one example of how an embodiment 999 of a passengermodule may be customized or personalized to meet the needs of aparticular user. The user may store items in the passenger module forvarious purposes. Some items may be stored in the main passengercompartment, while other items are stored in a trunk (not shown)provided in the passenger module. The passenger module may bepersonalized to accommodate and support various social, sports, andbusiness activities of the individual user. For example, items such asgolf clubs, gym bags, tennis rackets, clothing items, etc., may bestored in either a trunk or in the main passenger compartment of thepassenger module. The passenger module embodiment shown in FIG. 10includes such items as a microwave oven 993; a work surface 992 andcomputer 983 for use by a seated occupant during autonomous travel; golfclubs 997; an entertainment system 995; a wardrobe or clothing stowage998; and a satellite dish 996. The module 999 may also include suchfeatures as A/C outlets 991 and media connections 988 (such as USB andaudio connections) found in conventional vehicles. Any of a variety ofother amenities may be incorporated into a given passenger module duringfabrication or added by an owner of the module. In the module 999, apassenger may during a single trip, for example, watch a movie or video,work on the computer, and prepare a snack in the microwave oven whiletraveling from an office or home to a golf course for a golf game. Thepassenger module may be personalized to incorporate everything that auser may need for an entire week (or longer) of scheduled activities,thereby reducing the chances that a needed item may be forgotten by abusy or hurried user. A front portion of the passenger module 999 may besupported by one or more retractable legs 987 operable in the mannersimilar to leg(s) 499 a of FIG. 12 (described in greater detail below).Alternatively, the front portion of the module 999 may be supported in adifferent manner.

Referring to FIGS. 2-4C, an electrical/power connection module 49 may beprovided on the engine module 11 for operatively connecting to a similarelectrical/power connection module 69 located on the passenger module99. The modules 49 and 69 may include standardized complementaryconnectors and/or plug-in connections which facilitate quick coupling ofthe passenger module electrical systems to the engine module 11, forpurposes of powering the various passenger module systems during theperiod when the engine module 11 is connected to the passenger module99. The housings of the modules and the structures of the connectionsmay be configured to facilitate automated docking of the engine moduleto the passenger module, automated separation of the engine module fromthe docking module, and quick-connection and disconnection of the enginemodule electrical systems from the passenger module systems. Theelectrical/power connections may be standardized to enable any enginemodule to be connected to any passenger module.

Embodiments of the engine module 11 may also include a docking mechanism51 for operatively connecting to a similar docking mechanism 67 locatedon the passenger module 99. The docking mechanisms 51, 67 may bestructured to mechanically couple the engine module 11 to the passengermodule 99, to enable the engine module to pull or otherwise move orpropel the passenger module 99 during travel for the uses and purposesdescribed herein. One embodiment of a docking mechanism is shown inFIGS. 4A-4C. This embodiment may be implemented for a front-wheel driveengine module. However, any alternative docking mechanism and proceduresuitable for the purposes described herein may be used.

In a particular embodiment (as shown in FIGS. 4A-4C), the engine moduledocking mechanism 51 and electrical/power connection module 49 may beco-located, and the passenger module docking mechanism 67 andelectrical/power connection module 69 may be co-located. This may enablethe electrical and mechanical connections between the engine module andthe passenger module to be effected at the same time. A front portion ofthe passenger module 99 may be supported by one or more retractable legs97 operable in the manner similar to leg(s) 499 a of FIG. 12 (describedin greater detail below). Alternatively, the front portion of the module99 may be supported in a different manner.

To operatively connect the engine and passenger modules 11 and 99 witheach other, in FIG. 4A, an engine module 11 moves along a road surfaceR1 in a rearward direction (direction “N” in FIGS. 4A-4C) of the enginemodule toward the passenger module 99. The engine module may include awheel 11 a positioned above the road surface so as to engage a firstrolling surface 99 a formed on the passenger module 99. Referring toFIG. 4B, as the engine module 11 continues to move toward the passengermodule, wheel 11 a contacts first rolling surface 99 a and begins toroll upwardly toward a second rolling surface 99 b. As the wheel 11 arolls up the surface 99 a, the engine module rotates about front wheels11 b, thereby lifting engine module rear wheels 11 c off of the roadsurface R1. Lifting the rear wheels 11 c of the engine module off theground enables the engine module/passenger module combination to besteered using the engine module front wheels 11 b. At the same time,rotation of the engine module body causes the engine moduleelectrical/power connection module 49 and docking mechanism 51 to alignwith the complementary passenger module electrical/power connectionmodule 69 and docking mechanism 67 on the passenger module.

Referring to FIG. 4C, as wheel 11 a reaches second rolling surface 99 band continues to roll along this surface, the engine moduleelectrical/power connection module 49 completes docking with (andelectrical coupling with) the passenger module electrical/powerconnection module 69. Also, the engine module docking mechanism 51completes docking to the passenger module docking mechanism 67. Thepassenger module is now electrically and mechanically connected to theengine module for purposes of propelling the passenger module to itsintended destination and/or for its intended purpose. The operativelyconnected modules 11 and 99 combine to form an autonomous passengervehicle. The docking procedure may be automatically controlled by theengine module computing system 14, using an automated docking capability73 and module docking sensors 28 a, 128 a (if needed) in operativecommunication with the computing system.

In one example, the automated docking capability may be implemented byutilizing machine-detectable visual markers such as AprilTags or similarmarkers. Such markers may aid autonomous orientation and positioning ofthe engine module with respect to the passenger module. Docking sensors128 a may include lasers and/or sonar to help calculate and monitor thedistances between the engine and passenger modules during docking.

While FIGS. 4A-4C show a single, centrally-positioned docking assistancewheel 11 a located on the engine module 11, other wheel configurationsare also possible. For example, a pair or wheels (not shown) may beused, with one wheel positioned on each side of the engine module 11 forengaging corresponding docking surfaces similarly positioned along sidesof the passenger module 99.

In a particular embodiment, the docking mechanism includes at least apair of docking ears extending from one of the engine module and thepassenger module, and at least a pair of associated cavities formed inthe other one of the engine module and the passenger module. Each cavityis structured to receive therein an associated docking ear duringdocking of the autonomous engine module with the passenger module. Inthe embodiment shown in FIGS. 4A-4C, a pair of docking ears 51 a islocated on engine module 11 and cavities 67 a for receiving the dockingears are located on the passenger module 99. Although the embodimentshown uses a single pair of docking ears (one along each of the left andright sides of the engine module), any number of docking ears andassociated cavities may be used. A securement mechanism (generallydesignated 79) may be provided in one of the engine module and thepassenger module for securing the docking ears in their associatedcavities when the modules are docked and during operation of theautonomous passenger vehicle, thereby maintaining the autonomous enginemodule in a docked condition with the passenger module during travel ofthe engine module and the passenger module when passenger module isoperatively connected to the engine module. The securement mechanism 79may be in the form of a suitable pin or latch mechanism which isactuatable automatically by the engine module computing device whendocking sensors 28 a and/or 128 a determine that the modules are docked.Alternatively, any of a variety of other docking mechanisms may be used.

Detachment of the engine module 11 from the passenger module may followa reverse procedure. The securement mechanism 79 may be disengaged topermit the docking ears 51 a to be removed from their associatedcavities 67 a. The engine module 11 may then move slowly in a forwarddirection of the module (direction “M”) disengaging the electricalconnection modules and docking mechanisms as the wheel 11 a rolls alongpassenger module surface 99 b. As the engine module moves forward, wheel11 a rolls down surface 99 a until the engine module rear wheels aregrounded.

FIGS. 11 and 11A show an alternative embodiment of a docking mechanism.In the embodiment shown in FIGS. 11 and 11A, prior to docking, a frontportion of passenger module 399 is supported by one or more retractablelegs 399 a. In one example, a pair of legs 399 a is spaced apart along alateral or width dimension of the passenger module 399, on an undersideof the module. Legs 399 a are structured to support a front end 399 f ofthe passenger module 399 when the passenger module 399 is not dockedwith an engine module. The legs 399 a may be structured to beretractable (for example, by rotation from the deployed supportpositions “AA” shown in FIG. 11 to stowed or retracted positions “BB”(FIG. 11A)) when the passenger module front end 399 f is supported by anattached engine module 311 after docking.

In the embodiment shown in FIG. 11, a pair of posts 311 p and 311 r maybe provided along an upper surface 311 s of the engine module 311. Achannel or rail 380 may be attached to an underside of the passengermodule 399. The channel 380 may be structured to receive posts 311 p and311 r therein as the engine module 311 travels in direction “N” to dockwith the passenger module 399. During docking, to align the posts 311 pand 311 r with the passenger module channel 380 for docking, sensors(for example, cameras, lidar, ultrasonic ranging and/or other sensors)on the engine module 311 may register on APRILtags or otheridentifier(s) located on the passenger module 399. The computing systemof the engine module 311 may be configured to control the engine moduleto adjust the position and/or heading of the engine module to facilitatealignment. When the engine module 311 is aligned with the passengermodule 399 for docking, the engine module 311 may back into engagementwith the passenger module 399, forcing posts 311 p and 311 r into thepassenger module channel 380.

As the engine module moves in direction “N”, posts 311 p and 311 r movealong the passenger module channel 380 until the rear post 311 r reachesa predetermined position, at which point a locking mechanism 381 engagesthe rear post 311 r to lock the rear post in the predetermined position.The engine module is now docked with the passenger module as shown inFIG. 11A. Connection of the electrical systems of the engine andpassenger modules may be performed as described with respect to FIGS.4A-4C. In the embodiment shown in FIG. 11, element 349 may be an enginemodule electrical/power connection module similar to module 49 of FIGS.4A-4C, and element 369 may be a passenger module electrical/powerconnection module similar to module 69.

The locking mechanism 381 may automatically engage the rear post 311 rwhen the post reaches the predetermined position during docking.Alternatively, the passenger module 399 may incorporate one or moresensors (not shown) configured to detect when the rear post 311 r is inthe predetermined position. The sensors may be coupled to the passengermodule computing system. The computing system of passenger module 399may be configured to, responsive to input from the sensors, actuate thelocking mechanism 381 to lock the rear post 311 r in position relativeto the passenger module. Alternatively, the locking mechanism may beactuated manually. The locking mechanism 381 maintains the passengermodule 399 in a docked condition with the engine module 311 duringoperation of the autonomous passenger vehicle formed by docking theengine module with the passenger module, and until the locking mechanism381 is disengaged. Any type of locking mechanism suitable for thepurposes described herein may be used.

The computing system of engine module 311 may be configured to controlthe suspension of the engine module front wheels 311 b and rear wheels311 c so as to slightly raise the engine module after the rear post 311r engages the locking mechanism 381 on the passenger module 399, therebyrelieving pressure on the legs 399 a. Relieved of supporting the weightof the passenger module front end 399 f, the legs 399 a may be retractedinto positions “BB”. A computing system in either the engine module 311or the passenger module 399 may be configured to operate the legs 399 aso as to retract the legs after the passenger module weight has beentransferred from the legs 399 a to the engine module 311, and alsoconfigured to extend the legs 399 a to their support positions prior towithdrawal of the posts 311 p and 311 r from the passenger modulechannel 380. Alternatively, movement of the legs 399 a between thesupport and retracted positions may be done manually. For example, acomputing system in either the engine module 311 or the passenger module399 may be configured to provide a signal indicating that the frontportion of the passenger module is being supported by the engine module311. Upon receipt of this signal, the user may manually retract the legs399 a. After the legs 399 a have been retracted, the engine modulesuspension may be operated to return the engine module 311 to its normaloperating height.

To disengage the engine module 311 from the passenger module 399, theprocedure described above may be reversed. The engine module suspensionmay be controlled to raise the engine module 311 and the front portion399 f of the passenger module where the legs 399 a are located. The legs399 a may then be lowered to support the front portion 399 f of thepassenger module 399. The engine module suspension may then be operatedto return the engine module 311 to its normal operating height, afterwhich the locking mechanism 381 may be disengaged. The engine module maythen be moved forwardly (in a direction opposite direction “N”) toremove the posts 311 p and 311 r from the channel and disengage theengine module 311 from the passenger module 399.

FIG. 12 shows another embodiment 499 of a passenger module in a dockingarrangement similar to the embodiment shown in FIGS. 4A-4C. In thisembodiment, prior to docking, a front portion of passenger module 499 issupported by one or more retractable legs 499 a. In one example, a pairof legs 499 a is spaced apart along a lateral or width dimension of thepassenger module 499, on an underside of the module. Legs 499 a arestructured to support a front end of the passenger module 499 when themodule is not docked with an engine module. The legs 499 a may bestructured to be retractable (for example, by rotation from the deployedsupport positions “AA” shown in FIG. 12 to stowed or retracted positions“BB”) when the passenger module front end is supported by an attachedengine module 411 after docking.

To align the engine module 411 with the passenger module 499 fordocking, sensors (for example, cameras, lidar, ultrasonic ranging and/orother sensors) on the engine module 411 may register on APRILtags orother identifier(s) located on the passenger module 499. The enginemodule computing system may be configured to control the engine module411 to adjust the position and/or heading of the engine module tofacilitate alignment. When the engine module 411 is aligned with thepassenger module 499 for docking, the engine module 411 may back (indirection “N”) into engagement with the passenger module 499 aspreviously described with respect to FIGS. 4A-4C until the modules 411and 499 are docked. In the embodiment shown in FIG. 12, element 449 maybe an engine module electrical/power connection module similar to module49 of FIGS. 4A-4C, element 469 may be a passenger moduleelectrical/power connection module similar to module 69, element 451 maybe a docking mechanism similar to docking mechanism 51, and element 467may be a docking mechanism similar to docking mechanism 67.

In this embodiment, the docking mechanisms and connections previouslydescribed may be strengthened and modified to enable the weight of theautonomous passenger vehicle between the engine module wheels 411 b andthe passenger module wheels 499 w to be supported during operation ofthe vehicle. A computing system in either the engine module 411 or thepassenger module 499 may be configured to operate the legs 499 a so asto retract the legs after docking of the engine module 411 with thepassenger module 499, and also to extend the legs to their supportpositions prior to disengagement of the docked engine module from thepassenger module as previously described with respect to FIGS. 4A-4C.Alternatively, movement of the legs 499 a between the support andretracted positions may be done manually. For example, a computingsystem in either the engine module 411 or the passenger module 499 maybe configured to provide a docking confirmation signal detectable by auser. Upon receipt of this signal, the user may manually retract thelegs 499 a. In addition to those described above, any of a variety ofother docking mechanisms and arrangements may be utilized.

Referring to FIGS. 5 and 6, embodiments of the engine module 11, thepassenger module 99, and the computing systems described herein may beincorporated into various embodiments of a transportation system. Acomputing system as described herein for determining suitable autonomousengine module use candidates and for performing related functions may beembodied in one or more computing devices external to any of the enginemodules and/or passenger modules described herein. FIG. 6 shows anexample of a transportation system 100 incorporating such an embodiment.In this embodiment, the transportation system 100 includes at least onepassenger module 100 c and a plurality of engine modules 111-1, 111-2,111-3, and 111-4. Each engine module may be configured to operativelycouple with the passenger module to form an autonomous passengervehicle. This embodiment also includes a computing system 113 separatefrom the engine modules and configured as shown in FIG. 1, to implementthe engine module use candidate determination capability and make enginemodule use candidate determinations. For example, the computing system113 may be a central computer located at a roadside facility.Communications between a user 100 a, the passenger module 100 c, thecomputing system 113, and the engine modules may be enabled by awireless or other communications network 100 b through which elements ofthe transportation system 100 can communicate with the communicationsinterfaces in the engine modules and communications interfaces 113 kcoupled to the computing system 113. The user 100 a may communicate withthe computing system 113 directly (for example, via a wired connection)or wirelessly via the communications network.

Alternatively, the computing system may, for example, be embodied in adecentralized computing system embodied in a plurality of autonomousengine modules of a transportation system, as described herein. Atransportation system embodiment 200 incorporating such a computingsystem is shown in FIG. 5. This embodiment includes at least onepassenger module 200 c and a plurality of engine modules 211-1, 211-2,211-3, and 211-4. Each engine module may be configured to operativelycouple with the passenger module 200 c to form an autonomous passengervehicle. In this embodiment, the computing system performing the moduleuse candidate determination is embodied in the collection of enginemodules. Each engine module may be configured as previously describedwith respect to FIG. 2, including a version of the engine module usecandidate determination capability 71 described herein. Each enginemodule computing system may perform the necessary evaluations anddeterminations on itself (i.e., each engine module is“self-evaluating”), to determine its suitability for the intended use.In addition, the engine modules are configured to communicate with eachother either directly or via a wireless or other communications network200 b. The user 200 a may communicate with any or all of the enginemodules via the communications network through the communicationsinterfaces in the engine modules.

As previously described, various computing system embodiments (such ascomputing system 13 in FIG. 1 and engine module computing system 14 ofFIG. 2) may be configured to implement an embodiment of an autonomousengine module use candidate determination capability. The use candidatedetermination capability may be stored in a computer system-accessiblememory and implemented in the form of computer-readable program codethat, when executed by a processor, implement one or more of the variousprocesses, instructions or functions described herein. By thiscapability, an embodiment of the computing system may be configured toevaluate autonomous engine module requests received from a user or otherentities and to determine, responsive to a request and based oninformation in the request and other pertinent information (asavailable) at least one autonomous engine module use candidate from aplurality of autonomous engine modules. The autonomous engine module usecandidates may be engine modules which are deemed to best meet thepreferences and/or requirements of a particular proposed use. Theautonomous engine module candidates may be selected from a pool ofautonomous engine modules (for example, the group of engine modules211-1 through 211-4, plus any other engine modules in the group of FIG.5) that are maintained and allocated for use in propelling passengermodules that are dockable with the engine modules.

FIG. 7 is a flow diagram illustrating a method of selecting an enginemodule based on a request for use, and of providing a selected enginemodule to a user for use at a desired time and place. Some of the stepsdescribed may be performed by a user or other requesting entity, andsome of the steps may be performed by a computing system performing theengine module determination. For example, in the embodiment shown inFIG. 7, blocks 510, 520 and 540 may be performed by a computing systemas described herein.

In block 502, a request for engine module use may be generated via auser interface such as, for example, a cellular phone application, aninterface located in the passenger module, or from another terminalconnected to the Internet. Any suitable interface may be used. A requestfor use of an autonomous engine module or an “autonomous engine modulerequest” may be any request for use of an autonomous engine modulereceived from a transportation system user, a group of users, anorganization, or any other source. The computing system interface orrequest application may be configured to enable the user to specify oneor more user preferences, from a menu, for example. Examples of suchpreferences may include budgetary requirements, cost limitations, or arequest to minimize travel costs; selection of a preferred source orprovider for the engine module; trip start location; one or moredestinations; an order in which multiple destinations should be traveledto; a type of driving desired (for example, either “relaxed” or“shortest time to destination”); a type of fuel desired (for example,gasoline, diesel, hybrid-electric, electric); whether the engine moduleis intended to tow an object, such as a trailer; an expected number ofpassengers; proposed date(s), start time(s), and length(s) of usage; andany other pertinent information.

If desired, a passenger module identifier tag or a passenger moduleinformation file may be attached to the request for use. The identifiertag and the information file both contain information relating to thepassenger module to which the request for use pertains. The identifiertag may include an alphanumeric designation representing information onpassenger module characteristics which may be useful to a computingsystem in making engine module use candidate determinations. Passengermodule information associated with each identifier may be available froma database stored in a memory. The information file may include thepassenger module characteristic information. Such information mayinclude, for example, the passenger module weight (empty), overalldimensions, available cargo or storage space (including trunk size), thenumber of passenger seats, estimated maximum electrical powerrequirements (for example, if all power outlets and passenger-relatedsystems are running simultaneously); information regarding the sensorspresent on the passenger module, and any other pertinent information.The generated request may be transmitted (via a suitable communicationssystem) to a computing system for processing.

In block 505, the generated request may (if necessary) be transmitted toone or more computing systems for the module use candidate determinationprocess. For example, if the request was made using an interface inoperative communication with a computing system configured to make theuse candidate determination, transmission to a computing system may notbe necessary. In a transportation system configured as shown in FIG. 5,the request may be received by one or more of the engine modules 211-1through 211-4. The receiving module(s) may then relay the request to allof the other engine modules in the network, either directly or viacommunications network 200 b. This ensures that each engine modulereceives the request for individual processing. A protocol may beestablished for designating one of the engine modules as a “receivingmodule”, for receiving messages from the user/requester which will beforwarded to other engine modules in case they were not received in theoriginal transmission, and for receiving messages from the other enginemodules which are forwarded to the user/requester. For example, anengine module which is closest geographically to the requesting entitymay be designated the receiving module. In a transportation systemconfigured as shown in FIG. 6, the request may be received by thecomputing system 113 which executes the determination process.

In block 510, a computing system determines, responsive to the requestfor use of an autonomous engine module, at least one autonomous enginemodule use candidate from a plurality of autonomous engine modules. Indetermining the engine module use candidates, the computing systemexecuting the evaluation may be configured to compare parameters of therequested usage with the availabilities and capabilities of each enginemodule. In evaluating a given engine module for a proposed usage, theengine module features and capabilities may be compared withcharacteristics of the proposed use, as stated in the request and asdetermined or assumed by the computing system based on requestinformation and other information.

Engine modules may be eliminated as usage candidates based on failure tosatisfy usage requirements or preferences. In addition, some enginemodules which are deemed suitable as candidates may be given higherpriority as use candidates than other suitable modules, based on theirability to better satisfy usage requirements or preferences. Thedetermination process results in a list of one or more use candidatesdeemed most suitable for the intended use. Information regarding thesecandidates is incorporated into a notification generated forpresentation to a user.

Determination of at least one autonomous engine module use candidate mayinclude determining what information is included in the autonomousengine module request, and processing of this information using one ormore tools stored in memory, such as algorithms, lookup tables,equations, functions, comparisons with predetermined thresholds, and anyother suitable tools configured to aid in selecting one or moreautonomous engine modules which may satisfy all (or as many as possible)of the requirements and preferences set forth in the request. Based onthe descriptions provided herein and on various usage evaluationcriteria determined by the engine module and passenger module OEM's, oneskilled in the art may provide tools for this purpose using knowntechniques, for example, by identifying criteria for evaluatinginformation provided in the request, and assigning a priority and/orvalue to each criterion. Usage request information may also be assignedgreater or lesser weights for evaluation purposes depending on, forexample, the information content and/or the presence or absence of theinformation in the request. The information describing the requestedusage is then compared with the known characteristics and capabilitiesof the engine module to determine suitability for the intended usage.

FIG. 8 is a schematic block diagram illustrating examples of enginemodule evaluation criteria usable for determining at least oneautonomous engine module use candidate from a plurality of autonomousengine modules as set forth in block 510 of FIG. 7. Other criteria mayalso be employed. The engine module may be evaluated for suitability forthe proposed usage using one or more than one criteria, according toinformation in the usage request and any other available information.The blocks shown in FIG. 8 need not necessarily be executed in anyparticular order. In addition, some blocks may not be executed if theinformation available is insufficient for evaluation. For example, ifthe usage request does not specify a fuel-type preference or informationis not available on passenger module characteristics, the proposed usagemay not be evaluated using these criteria, and one or more engine modulecandidates may be selected based only on whatever information isprovided by the user. For example, if a user specifies only a desireddate and time of usage, one or more engine module candidates may bedetermined based solely on engine module availability at the desireddate and time. This may enable the user to simplify the engine moduledetermination process. For example, the user may own a simple, standardor relatively lightweight passenger module and may need an availableengine module as soon as possible. Cost or other possible evaluationparameters may be relatively unimportant. In this case, simplificationof the engine module determination process may increase the number ofpotential engine module candidates, thereby increasing the likelihoodthat an engine module will be available on the date and time needed. Ina similar manner, the pool of possible engine module candidates may beexpanded by specifying as few evaluation parameters as possible. Incertain embodiments, some of the evaluation criteria shown in FIG. 8 maybe interrelated. For example, the planned route (block 720) may affectthe cost of the propose usage (block 730). In such cases, the computingsystem may be configured to determine a specific order for performanceof the blocks and/or to perform the blocks shown in a specific orderdesigned to facilitate the engine module determination.

Criteria for evaluating the suitability of any particular engine modulefor a given application may include such factors as engine moduleavailability during the requested date and time for the desired usageperiod, the characteristics of the passenger module (such as passengermodule weight and overall dimensions, which sensors are present orabsent on the passenger module, and similar factors), the planned routeor routes, whether the engine module is to tow an object in addition topropelling the passenger module, and any other pertinent factors. One ormore of these criteria may be used as key thresholds for determining thesuitability of a particular engine module for a proposed use. That is,if it is considered necessary for an engine module to satisfy one ormore of the above thresholds, the module may be eliminated fromconsideration as a use candidate if it fails to meet the requiredthreshold(s). Other evaluation criteria may include the estimated costof the proposed usage, whether the user has a preferred vendor orsupplier of the engine module, the type of driving desired by the user,user fuel preference (e.g., diesel, hybrid, electric, gasoline), andother factors. In particular embodiments, one or more of theseparameters may be specified by a user as previously described. Thecomputing system may be configured to (through its determinationprocedures and tools) determine an engine module use candidate (orcandidates) deemed most suitable for meeting all of the transportationand user requirements for the proposed use, or as many of therequirements as possible.

In block 710, the computing system may_evaluate engine moduleavailability during the requested date and time for the desired usageperiod may be determined by comparing the proposed usage period with aknown schedule of the engine module.

In block 715, the computing system may evaluate the passenger modulecharacteristic information (such as weight, size, etc.) as previouslydescribed by reviewing any available passenger module characteristicsand determining if the engine module in question may be appropriate forpropelling the passenger module as desired and/or required during theproposed usage. This may be done by determining if this information isincluded in the autonomous engine module use request. For example, for arelatively heavier passenger module, an engine module with a morepowerful engine may be appropriate.

In block 720, the computing system may evaluate the suitability of theengine module with regard to a planned route of the vehicle during theproposed usage. The computing system may (in conjunction with anavigation unit or system) determine one or more possible routes basedon start and end locations provided by the user. The computing systemmay be configured to make estimations or determinations (such as trafficdensities at locations along the route during the usage time, forexample) regarding the route. These estimations may be factored into theuse candidate determination. For example, if a planned route involves90% expressway travel, selection of an engine module having a relativelyhigher fuel-efficiency may be indicated. In another example, if aplanned route or a desired type of driving involves a high percentage(as determined by comparison with a predetermined threshold) ofrelatively high-speed driving, an engine module having a relativelyhigher horsepower may be more appropriate.

In block 725, the computing system may evaluate the engine module withregard to whether the engine module is to both propel the passengermodule and tow an object behind the passenger module. For example, ifthe proposed engine module usage involves towing a trailer as well asthe passenger module, or the passenger module has a weight above acertain threshold, an engine module capable of generating a relativelyhigher torque may be needed. If the information is not included in therequest, or if the information in the request indicates that no objectis to be towed by the passenger module, the computing system may assumethat no object is to be towed and determine suitable engine modulecandidates on that basis.

In block 730, the computing system may evaluate the engine module withregard to the total cost of the proposed usage. The cost of the proposedusage may be estimated and itemized, with reference to availableinformation, such as features of the planned route, the fuel preference,the type of driving desired, the fuel cost per travel mile, and the costof renting the unit over the proposed usage period. Engine modulesoffering the lowest total usage cost (within the desired and/or requiredusage parameters) may be selected by the computing system forpresentation to the user.

In block 735, the computing system may evaluate the engine module withregard to whether it is controlled, owned, or leased by a user-preferredvendor. The user's choice of engine module vendor may be considered. Thecomputing system may attempt to identify modules which meet usagerequirements and which are available from the requested vendor. If avendor does not offer (or have available at the requested time) a modulewith a capability deemed necessary for the proposed use, this may beindicated to the user, along with possible alternative engine modulesand vendors.

In block 740, the computing system may evaluate the engine module withregard to a type of driving desired by the user. For example, if theuser desires a relaxed or leisurely (i.e., non-hurried) trip, an enginemodule which may generate less horsepower may be used. Alternatively, ifthe user desires minimum travel time to a destination, an engine modulewhich may generate more horsepower may be more appropriate.

In block 745, the computing system may evaluate the type of fuel used bythe engine module with regard to a user fuel preference (e.g., diesel,hybrid, electric, gasoline).

In block 750, the computing system may evaluate engine module withregard to the number, types and/or locations of sensors mounted on thepassenger module. If certain types of sensors are not available on agiven passenger module, it may be desirable to specify possible enginemodules for selection which incorporate such sensors and/or which havesuch sensors configured such that the lack of the sensors on thepassenger module may be compensated for.

The list of criteria shown in FIG. 8 is not exhaustive, and the enginemodule may also be evaluated on additional or alternative criteria, ifdesired.

In particular embodiments, the various parameters considered in the usecandidate determination may be prioritized and/or weighted, according topre-programmed instructions or by a user prior to determination of thecandidates. A flow diagram illustrating an example of such a process isshown in FIG. 9. In block 610, the requirements of the particulartransportation need may be evaluated first or given priority over userpreferences (such as cost and fuel-type preference, for example). Theinability of some engine modules to meet use requirements may eliminatethese modules from consideration as possible use candidates because, forvarious reasons, they may not be able to satisfy the requested usage.For example, unavailability of an engine module at the requested usagetime, or the inability of the engine module to effectively propel theestimated weight of the passenger module or the passenger module and atrailer may eliminate the module from consideration. Thus, at least oneof these parameters and other, similar parameters may be examined first,as key threshold parameters.

In block 620, after evaluating the engine modules for the ability tomeet key thresholds, the engine modules not eliminated by the evaluationof the “use requirements” parameters may be evaluated for suitabilitybased on the ability to meet other parameters, such as at least oneuser-defined preference. Examples of such user preferences may includefuel-type preferences, engine module vendor preferences, requestedbudget, and type of driving as described above.

In block 630, after evaluation of the engine module with regard to keythresholds and user preferences, the computing system may evaluate theengine module for the proposed usage using any other criteria deemedpertinent to engine module selection. In addition, a user may change thecategorization of any given parameter to a threshold parameter if thisparameter is considered to be especially important to the user. Thecomputing system may determine the engine module use candidates whichbest meet as many of the key threshold and user preference criteria aspossible, with the meeting of key threshold criteria being givenpriority for functional reasons. If no suitable use candidates are foundby the determination process, a message to this effect may be sent tothe requester in a notification (described below).

In a transportation system configured as shown in FIG. 6, in which acomputing system outside the modules conducts the use candidatedetermination, the analysis described above may be performed bycomputing system 113 for each individual engine module of the pluralityof modules in the transportation system. The computing system 113determines the most suitable candidate(s). The computing system 113 mayhave stored in memory information (designated 13 j in the exemplarycomputing system 13 of FIG. 1) relating to the various autonomous enginemodules 111-1 through 111-4 in a network (or under the control) of thecomputing system 113.

Referring to FIGS. 2 and 5, in a transportation system configured asshown in FIG. 5, the computing systems of individual engine modules 211configured as shown in FIG. 2 may incorporate the same or substantiallythe same control logic as previously described with regard to computingsystem 13 (FIG. 1), for determining the engine module use candidates andfor performing the other, related functions described. Thus, thecomputing system in each individual engine module 211 may be configuredto receive an engine module request from a user or other entity,including a request that may have been received by another engine moduleand relayed to one or more additional modules in a network or pluralityof modules via a communications network. However, the use candidatedetermination capability may be adapted in certain respects. Forexample, the computing systems of the individual engine modules may beconfigured to communicate and exchange information with each other forpurposes of identifying suitable engine module use candidates for theproposed usage.

In addition, the computing system in each engine module may beconfigured to “self-evaluate” the suitability of the engine module inquestion for meeting user needs and requirements for a particularsituation. Based on the self-evaluation, any given engine module mayexclude itself from further consideration as a possible use candidate,for example due to scheduling conflicts, cost, estimated type of usage,or other factors as described above. Each self-evaluating engine modulein the network may be configured to notify the receiving engine moduleas to whether or not the self-evaluating engine module determines itselfto be suitable for the proposed use. The receiving module may beconfigured to maintain a record of the suitable modules for use ingenerating a notification to the user/requester.

Referring back to FIG. 7, in block 520, when the above-described processis complete and one or more engine modules deemed suitable for theintended use have been determined, the computing system may generate anotification directed to a user including information relating to the atleast one engine module use candidate. The notification may also prompta user to select or confirm for use one of the proposed engine moduleuse candidates. In a transportation system configured as shown in FIG.5, the notification may be generated and transmitted to therequester/user by the designated receiving engine module.

In block 530, a user/requester may select (from a group of possibleautonomous engine modules if more than one possible module is presented)or confirm (if only a single possible module is presented) an enginemodule that may be forwarded to connect with the user's passenger moduleon the selected usage date(s).

In block 540, responsive to user selection or confirmation of an enginemodule use candidate for use, a computing system (such as computingsystem 113 of FIG. 6 or a receiving engine module in the transportationsystem of FIG. 5) may provide a notification to the engine modulecandidate selected or confirmed for use. The information in thenotification may include the date and time the selected engine module isto arrive at a designated location for docking or operative coupling tothe passenger module, the length of time the engine module is to beused, the location of the passenger module at the designated time, usercontact information, and any other information pertinent to locatingand/or docking with the passenger module at the designated time. If theusage parameters or requirements need to be revised prior to thescheduled date, a new usage request may be initiated starting in block502 and proceeding as just described.

In block 550, when the time for the scheduled use arrives, the selectedengine module may drive itself to the designated pickup location, usingthe self-driving capability 83 previously described. For example,referring to FIG. 5, in a transportation system configured as shown,execution of the use candidate determination and selection process mayresult in the selection of engine module 211-1. This engine module woulddrive itself to the location of passenger module 200-c in time for therequested usage. Similarly, referring to FIG. 6, in a transportationsystem configured as shown, execution of the use candidate determinationand selection process may result in the selection of engine module111-1. This engine module would drive itself to the location ofpassenger module 100-c in time for the requested usage.

In the above detailed description, reference is made to the accompanyingfigures, which form a part hereof. In the figures, similar symbolstypically identify similar components, unless context dictatesotherwise. The illustrative embodiments described in the detaileddescription, figures, and claims are not meant to be limiting. Otherembodiments may be utilized, and other changes may be made, withoutdeparting from the scope of the subject matter presented herein. It willbe readily understood that the aspects of the present disclosure, asgenerally described herein, and illustrated in the figures, can bearranged, substituted, combined, separated, and designed in a widevariety of different configurations, all of which are explicitlycontemplated herein.

As will be appreciated by one skilled in the pertinent art upon readingthe disclosure, various aspects described herein may be embodied as amethod, a computer system, or a computer program product. Accordingly,those aspects may take the form of an entirely hardware embodiment, anentirely software embodiment or an embodiment combining software andhardware aspects. Furthermore, such aspects may take the form of acomputer program product stored by one or more computer-readable storagemedia having computer-readable program code, or instructions, embodiedin or on the storage media for executing the functions described herein.In addition, various signals representing data, instructions or eventsas described herein may be transferred between a source and adestination in the form of electromagnetic waves traveling throughsignal-conducting media such as metal wires, optical fibers, and/orwireless transmission media (e.g., air and/or space).

The terms “a” and “an,” as used herein, are defined as one or more thanone. The term “plurality,” as used herein, is defined as two or morethan two. The term “another,” as used herein, is defined as at least asecond or more. The terms “including” and/or “having,” as used herein,are defined as comprising (i.e. open language). The phrase “at least oneof . . . and . . . ” as used herein refers to and encompasses any andall possible combinations of one or more of the associated listed items.As an example, the phrase “at least one of A, B and C” includes A only,B only, C only, or any combination thereof (e.g. AB, AC, BC or ABC).

Aspects herein can be embodied in other forms without departing from thespirit or essential attributes thereof. Accordingly, reference should bemade to the following claims, rather than to the foregoingspecification, as indicating the scope of the invention.

What is claimed is:
 1. A transportation system comprising: at least onepassenger module; and at least one autonomous engine module configuredto operatively couple with the at least one passenger module to form anautonomous passenger vehicle.
 2. The transportation system of claim 1further comprising a plurality of autonomous engine modules, each enginemodule being configured to operatively couple with the at least onepassenger module to form an associated autonomous passenger vehicle. 3.The transportation system of claim 2 further comprising a computingsystem configured to determine, responsive to a request for use of anautonomous engine module, at least one autonomous engine module usecandidate from the plurality of autonomous engine modules.
 4. Thetransportation system of claim 3 wherein the computing system isembodied in the plurality of autonomous engine modules.
 5. Thetransportation system of claim 2 wherein at least one engine module ofthe plurality of autonomous engine modules is optimized to generate arelatively high torque.
 6. The transportation system of claim 2 whereinat least one engine module of the plurality of autonomous engine modulesis optimized to provide a relatively high fuel-efficiency.
 7. Thetransportation system of claim 2 wherein at least one engine module ofthe plurality of autonomous engine modules is optimized to generate arelatively high horsepower.
 8. The transportation system of claim 1further comprising a docking mechanism for operatively connecting the atleast one autonomous engine module to the at least one passenger module,the docking mechanism comprising: at least a pair of docking earsextending from one of the at least one engine module and the at leastone passenger module; at least a pair of associated cavities formed inthe other one of the at least one engine module and the at least onepassenger module, each cavity of the at least a pair of associatedcavities being structured to receive therein an associated docking earof the at least a pair of docking ears during docking of the at leastone autonomous engine module with the at least one passenger module; anda securement mechanism structured for securing the at least a pair ofdocking ears in the at least a pair of associated cavities so as tomaintain the at least one autonomous engine module in a docked conditionwith the at least one passenger module during travel of the at least oneautonomous engine module and the at least one passenger module when theat least one passenger module is operatively connected to the at leastone autonomous engine module.
 9. The transportation system of claim 1further comprising a docking mechanism for operatively connecting the atleast one autonomous engine module to the at least one passenger module,the docking mechanism comprising: a pair of posts provided along anupper surface of the at least one autonomous engine module; a channelpositioned on an underside of the at least one passenger module, thechannel being structured to receive the pair of posts therein duringdocking of the at least one engine module with the at least onepassenger module; and a locking mechanism positioned on the at least onepassenger module, the locking mechanism being structured to engage atleast one post of the pair of posts to maintain the at least onepassenger module in a docked condition with the at least one enginemodule until the locking mechanism is disengaged.
 10. The transportationsystem of claim 1 further comprising a docking mechanism for operativelyconnecting the at least one autonomous engine module to the at least onepassenger module, the docking mechanism comprising: at least oneretractable leg structured to be extendable for supporting a portion ofthe at least one passenger module when the at least one passenger moduleis not docked with an engine module; wherein the at least one leg isconfigured to be retractable after docking of the at least one enginemodule with the at least one passenger module, and wherein the at leastone leg is configured to be extendable to a position supporting aportion of the at least one passenger module prior to disengagement ofthe at least one engine module from the at least one passenger module.11. A computing system comprising one or more processors for controllingoperation of the computing system, and a memory for storing data andprogram instructions usable by the one or more processors, wherein theone or more processors are configured to execute instructions stored inthe memory to determine, responsive to a request for use of anautonomous engine module, at least one autonomous engine module usecandidate from a plurality of autonomous engine modules.
 12. A computingsystem in accordance with claim 11 embodied in the plurality ofautonomous engine modules.
 13. The computing system of claim 11 whereinthe one or more processors are configured to execute instructions storedin the memory to, responsive to a determination of at least oneautonomous engine module use candidate, generate a notificationincluding information relating to the at least one engine module usecandidate.
 14. The computing system of claim 13 wherein the one or moreprocessors are configured to execute instructions stored in the memoryto prompt a user to select or confirm for use an engine module usecandidate responsive to the notification.
 15. The computing system ofclaim 14 wherein the one or more processors are configured to executeinstructions stored in the memory to, responsive to user selection orconfirmation of an engine module use candidate for use, provide anotification to an engine module use candidate selected or confirmed foruse, the notification including information relating to the request foruse of an autonomous engine module.
 16. A computer-implemented methodcomprising a step of determining, responsive to a request for use of anautonomous engine module, at least one autonomous engine module usecandidate from a plurality of autonomous engine modules.
 17. The methodof claim 16 wherein the step of determining at least one autonomousengine module use candidate comprises the step of evaluating each enginemodule in the plurality of autonomous engine modules with regard to atleast one key threshold parameter, to determine engine modules of theplurality of autonomous engine modules capable of satisfying the atleast one key threshold parameter.
 18. The method of claim 17 whereinthe step of determining at least one autonomous engine module usecandidate further comprises the step of evaluating each engine module ofthe plurality of engine modules capable of satisfying the at least onekey threshold parameter with regard to at least one user preference, todetermine engine modules of the plurality of engine modules capable ofsatisfying the at least one key threshold parameter and also capable ofsatisfying the at least one user preference.
 19. The method of claim 16further comprising the step of generating a notification includinginformation relating to the at least one engine module use candidate.20. The method of claim 19 wherein the notification includes a prompt toa user to select or confirm for use an engine module use candidateresponsive to the notification.
 21. The method of claim 20 furthercomprising the step of, responsive to the user selecting or confirmingan engine module use candidate for use, providing a notification to theengine module use candidate selected or confirmed for use, thenotification including information relating to the request for use of anautonomous engine module.
 22. The method of claim 16 wherein the step ofdetermining at least one autonomous engine module use candidatecomprises at least one of the steps of: evaluating an availability of atleast one engine module of the plurality of autonomous engine modulesduring a requested date and time for a desired usage period; evaluatingat least one engine module of the plurality of autonomous engine moduleswith regard to an estimated cost of a proposed usage of the at leastautonomous one engine module; evaluating at least one engine module ofthe plurality of autonomous engine modules with regard to a plannedroute relating to the request for use of an autonomous engine module;evaluating at least one engine module of the plurality of autonomousengine modules with regard to characteristics of a passenger modulerelating to the request for use of an autonomous engine module;evaluating at least one engine module of the plurality of autonomousengine modules with regard to whether an object is to be towed by apassenger module relating to the request for use of an autonomous enginemodule; evaluating at least one engine module of the plurality ofautonomous engine modules with regard to fuel preference of a user of apassenger module relating to the request for use of an autonomous enginemodule; evaluating at least one engine module of the plurality ofautonomous engine modules with regard to a type of driving desired by auser relating to the request for use of an autonomous engine module;evaluating at least one engine module of the plurality of autonomousengine modules with regard to an engine module vendor preference of auser relating to the request for use of an autonomous engine module; andevaluating at least one engine module of the plurality of autonomousengine modules with regard to which sensors are present or absent on apassenger module relating to the request for use of an autonomous enginemodule.
 23. A non-transitory computer readable medium having storedtherein instructions executable by a computer system to cause thecomputer system to perform functions, the functions comprising at leastdetermining, responsive to a request for use of an autonomous enginemodule, at least one autonomous engine module use candidate from aplurality of autonomous engine modules.
 24. A passenger vehiclecomprising: a passenger module; and an autonomous engine module withoutaccommodations for a passenger or a driver, the autonomous engine modulebeing configured to operatively couple with the passenger module to forman autonomous passenger vehicle.
 25. The passenger vehicle of claim 24wherein the passenger module is not configured for self-propulsion.